(Special Focus - Java Technologies)(Disc 1).ISO/products/Software/SiteScapeInc/lsummit.gif)
| Convention | Definition |
|---|---|
| > | The UNIX system prompt. |
| dispatch.cgi | Path names, directory names, file names, URLs, and commands and parameters that you have to enter as displayed are shown in the Courier type font. |
| Solaris: > tar | Instructions applicable only to one system platform are labeled as such. |
SiteScape, Inc. provides additional, exciting Forum services and Add-On products that are not documented here. For complete and up-to-date information on SiteScape Forum, its services, its Add-On products, and SiteScape's other product offerings, please visit the SiteScape web site.
You can communicate with other people by posting notes and replies in an online conversation, by requesting an appointment with another user, by having SiteScape Forum notify users through electronic mail when new information has been added, and by having online conferences in the form of a real-time "chat line." In addition to communicating, you can share resources with other people by sharing documents, by keeping a group or team calendar of meetings and events, and by searching Internet news sources and sharing those news articles with others.
The most common types of forums are as follows:
Summits are Forum's starting pages (or "home pages"). They provide a table of contents of the forums available for your use. And they provide you with access to commonly used tools, such as searching for users, access to personal tracking and work areas, searching for entries across forums, accessing Help, and performing administrative functions (if you have administrative privileges).Cascaded summit pages are those that are typically hierarchically linked to other summits. (Just as folders can contain links to subfolders, summits can contain links to cascaded summits.) So, you can have a summit page that is accessible to all employees in a company, and you can create cascaded summits for each of the company departments: Management, Marketing, Sales, Engineering, and so on.
These forums are collections of related topics and replies to those topics, which form online conversations. These forums can also contain collections of related documents. For instance, a hyperlink, "Widget X Project Version 2.0: Team Discussions," is connected to a listing of all of the topics for the Widget X Version 2.0 project team. One possible conversation topic could be, "Brainstorming: Ideas for Version 3.0." When you click on a hyperlinked topic, you can read the first note in the conversation.Another topic, "Widget X Project, Version 1.0 Interim Project Plan," is a document which you can view and edit. You can also use a document forum as a place where several people can co-author the same document and save its previous versions. Topics are located in folders within a folder hierarchy (folders that can contain other folders, and so on). Forum users can also add topic titles and delete them (if they created them).
These forums provide a method for searching through web pages, Internet newsgroups, or electronic mail subscriptions from Internet content providers, filtering the information, presenting selected news articles, editing those articles, and customizing the presentation of the news by adding graphics and new writing.
These forums allow a group of people to maintain and use a calendar of events and meetings. From within the calendar, you can have "real-time" communications (the person receiving the message can read it in a window on her or his machine almost at the same time you are typing it) with other Forum users or teammates.
This type of forum provides a private work area for a small group of people working toward a time-limited goal. This work area includes a private docshare forum, a calendar, a newspaper, and an easier ability to chat with each other.Teams can be created and disbanded quickly. All team members have the ability to administer the team area by changing team properties (adding a team member, removing a team member, changing the background color of the pages, and so forth).
This forum allows you to place files into Forum so that you or your teammates can have easier access to them. When you place files in this forum, you or your teammates can access the files using a web browser from your office, from home, while on a business trip, from a coworker's office, or from anywhere you are able to access the Forum summit page.
This type of forum provides you with a personal home page from which you can track activity in the other forums you use most often. This home page provides access to your favorite links to the World Wide Web, your personal calendar, your personal docshare forum, and your MyNews folders.There are two ways to track activity in other forums you use most often. You can view the "Notifications" folder in the MyNews section of the Tracker. You can also specify the name and URL of a particular forum you want to track, and the Tracker keeps a running total of all of the new and modified entries included in that forum since you last used it.
The Forum administrator can prevent the creation and use of personal calendars and docshares. Also, you cannot create MyNews folders until the administrator configures the newspaper forums. If you are not able to create and use these forums, contact your system administrator for more information.
SiteScape's first separately-purchasable Add-On product is called SiteScape Forum Workflow. The Workflow product adds tremendous power and customization flexibility to Discussion and Document-Sharing forums. Workflow builds in features that make team collaboration faster, easier, and more efficient, by structuring who must do the work (and who cannot participate), by structuring how the work must be done, and by clearly marking the current "state" of the work. A user can define types of Workflow processes using menus and user-friendly HTML forms; there is no need for additional programming.To get a better idea of the look-and-feel of a Workflow process, consider an "order-approval" process. With this type of process, a user places a request in the forum for new office equipment. Only the employee and his manager can see the request, and it is clearly marked "Requested." The manager receives e-mail alerting her to the equipment request, and, in the forum, she approves or rejects it by clicking on a button. If the entry is approved, a Purchasing Agent receives e-mail alerting him to the purchase request. The Purchasing Agent, again, by clicking on a button in the forum, rejects it or indicates that the office equipment is on order. Only those involved in the process can view the entry, and the entry always clearly shows the current state of the work (Requested, Approved, Rejected, Ordered).
For more information about Workflow, please visit the SiteScape web site.
SiteScape Forum also includes a set of sample applications that are customizations (slight alterations) of the functionality found in the Discussions and Document Sharing forums. These applications use new object technology offered to application programmers through SiteScape Forum Toolkit. Toolkit programmers can review the code for these forums to see an example of using Toolkit objects.
You may decide to create forum instances of these types, or you may want to delete them from your system. (For more information about deleting them from your system, see the "Creating a Forum" section in the Administrative Menus Help topic.) The following are customized forums available for your use:
Refer to the New Features topic in the online Help for a complete list of new and enhanced features in this version of SiteScape Forum.
In order for people to use SiteScape Forum, the Forum administrator needs to provide a Universal Resource Locator (URL), such as the following:
Netscape Servers: http://server.company.com/forums/aca-1/dispatch.cgi
Microsoft IIS Servers: http://server.company.com/forums/aca-1/dispatch.cgi
Apache web Servers: http://server.company.com/forums/aca-1/dispatch.cgi
The administrator assigns the URL to SiteScape Forum visible directory during the configuration process. The aca-1 directory contains the Forum CGI program.
Then, people can use Netscape Navigator or Microsoft Internet Explorer to open the URL and view the summit page. A summit page is a table of contents for all the resources (discussions, shared documents, news articles, and so forth) available to users. The summit page also allows users to register, allows administrators to access tools they need to keep Forum organized and running, and allows access to the Help system. If you choose, you can use the access-control features of SiteScape Forum to protect sensitive information or to require a password for participation.
SiteScape Forum provides a default look and feel for the summit page. However, if the system administrator chooses, she or he can customize this page, adding artwork and text.
In order for Forum authentication to work properly, users must make sure that cookie acceptance and notification are enabled in their web browsers. To enable Forum authentication, all SiteScape Forum users must have their browser's cookie property set to "always accept" or "notify before accepting."
[Beginning of this section] [Table of Contents]
|
Operating system |
Tru64TM UNIX«
(formerly Digital UNIX)
4.0b and up on an Alpha-based computer
Windows NT 4.0 and up with Service Pack 2, on an Intel -based computer (Service Pack 3 recommended for multiprocessor systems) Sun Solaris 2.5 and up, running on a Sun SPARC« computer Red Hat Linux Version 5.2 and 6.0. |
|---|---|
| System |
128 MB RAM minimum; 256+ MB preferred, and 200+ MHz
processor preferred 80 MB disk space, plus additional space for your user data. CD-ROM drive |
| HTTP (World Wide web) server |
Netscape Servers:
Apache Version 1.2 and up Microsoft Internet Information Server V3.0 (Windows NT 4.0 SP2), V4.0 |
| Web browser (installed on client systems) |
Netscape Navigator 3.01, and 4.0 through 4.7
Microsoft Internet Explorer 3.01, 3.02, 4.0, or 5.0 |
Please review the release.txt file (release notes) for the most up-to-date product information, including notices and restrictions. You can find this file on your SiteScape Forum CD, in the SiteScape Forum base directory (by default, /Avf ), or linked into the online Help system.
Windows NT Installation Procedure
Tru64 UNIX (formerly Digital UNIX) Installation Procedure
You must have a valid license key to properly install SiteScape Forum. The key should be included with your CDROM packaging. It has the following general format (FBnn-nnnn-nnnn-nnnn, where n is a number or letter whose case does not matter).
Warning: If you do not have a key, do not install this software--it will not work without a key. You can obtain a temporary key by visiting the SiteScape web site (temporary keys allow you to install the software, and use it for a brief period of time for evaluation purposes).
To obtain a temporary key or to obtain further information, contact us in either of the following ways:
http://www.sitescape.com/ support@sitescape.com
If it does not detect an existing installation, then the procedure continues with the next step.
SiteScape Forum creates three specific directories: one for the installed software and two for databases. One database contains files that are visible to browser users who are accessing your forums, and the other contains hidden files for internal use only. The default directories are as follows:
Hidden: C:\AVF\hidden
The identifier that you provide for these directories will be directly accessed by only system administrators. When you configure your web server, you will map an alias (for example, "forums") to the visible directory. When users access your summit page, they will type in the alias to access the visible directory, as follows:
http://www.company.com/forums/...
The alias of forums maps to the C:\AVF\visible directory.
For example, let's say that the purpose of your summit page is to discuss issues regarding sales of your product. So, you can specify sales as the ACA directory name. Then, users would have to type the following URL to access your summit:
http://www.company.com/forums/sales/dispatch.cgi
If the installation procedure reports a problem, check the file create-aca.log. Windows NT systems store installation and upgrade information in this file, which resides in the SiteScape Forum installation directory.
The software will not run without the installation of at least one valid license key.
If the the installation process detects an existing installation with valid license keys, then it displays a list of the keys, and it provides you with a chance to install additional keys. If you have no additional keys to install, click on the No button. If you have additional keys to install, click on the Yes button, provide the key, and click on the Next button.
You must have a valid license key to properly install SiteScape Forum. The key should be included with your CDROM packaging. It has the following general format ( FBnn-nnnn-nnnn-nnnn, where n is a number or letter whose case does not matter).
Warning: If you do not have a key, do not install this software--it will not work without a key. You can obtain a temporary key by visiting the SiteScape web site (temporary keys allow you to install the software, and use it for a brief period of time for evaluation purposes).
To obtain a temporary key or to obtain further information, contact us in either of the following ways:
http://www.sitescape.com/ support@sitescape.com
The device name ( rz*c ) and mount point ( mnt_point ) arguments are dependent on your specific installation. Also, Solaris machines automatically mount the CD and do not require issuing a command.
(Please forgive the red-letter assault on your eyes, but, like, umm, this is important!)
Solaris: > tar xf /cdrom/ssf50_1/solaris/ssf50so.tar
Red Hat Linux:
> tar xf /mnt/cdrom/linux/ssf50li.tar
> tar xf /mnt/cdrom/linux/ssf50li6.tar
The software will not run without the installation of at least one valid license key.
SiteScape Forum creates three specific directories: one for the installed software and two for databases. One database contains files that are visible to browser users who are accessing your forums, and the other contains hidden files for internal use only.
There are no default directory names. You may want to use the names visible and hidden for clarity.
The visible directory must be addressable by a URL given to your web server, and the hidden directory must not be addressable.
The identifier that you provide for these directories will be directly accessed by only system administrators. When you configure your web server, you will map an alias (for example, "forums") to the visible directory. When users access your summit page, they will type in the alias to access the visible directory, as follows:
http://www.company.com/forums/...
The alias of forums maps to the visible directory.
If you choose, you can supply a directory name that has meaning to your users. (For example, you can specify your company's name for a summit page used by the entire company, a team name for a summit used by a specific team, an identifier that speaks to the purpose of the discussions on this particular summit, and so forth.)
For example, let's say that the purpose of your summit page is to discuss issues regarding sales of your product. So, you can specify sales as the ACA directory name. Then, users would have to type the following URL to access your summit:
http://www.company.com/forums/sales/dispatch.cgi
root .
The installation script installs the background for the next reboot, and the script starts up Forum.
As your next step, you need to configure your web server.
[Beginning of this topic] [Table of Contents]
If the upgrade software encounters a very large docshare forum (with more than 1,000 entries), then the upgrade software may take a long time to complete the upgrade for that one forum, causing your system to appear as if it is hanging. (For a system with more than 300 megahertz of power, and for every 1,000 entries in the forum, the upgrade process for that forum takes a few minutes to complete. If your forum has 6,000 entries, it may take 15 to 20 minutes to complete work on that one docshare forum.)
Do not interrupt the process while it is upgrading a forum. If you do, use your back-up files to replace the database ( .webletdb* files). (If you did not back up your system before you began the upgrade, then you will have to work with the SiteScape support team to attempt to fix the WIM database, which may or may not be successful.)
Click on the appropriate link to view the upgrade procedures for that platform:
avf.conf
in the SiteScape
Forum base directory to change the read script
name for the web server you want to use:
ReadScriptName
should be
{dispatch.cgi}
Wgw-PlatformID
should be
{NT Netscape}
root .
avf-
background process with
the following command:
> ./avf-background stop
The device name ( rz*c ) and mount point ( mnt_point ) arguments are dependent on your specific installation. Also, Solaris machines automatically mount the CD and do not require issuing a command.
Solaris: > tar xf /cdrom/ssf50_1/solaris/ssf50so.tar
Red Hat Linux:
> tar xf /mnt/cdrom/linux/ssf50li.tar
> tar xf /mnt/cdrom/linux/ssf50li6.tar
The installation procedure lists the access control areas and Forums that are being updated.
root .
To deinstall SiteScape Forum, do the following:
root .
avf-
background process with
the following command:
> ./avf-background stop
/sbin/init.d/avfbackground
Solaris:
/etc/rc2.d/S95avfbackground
Click on the appropriate link to view the configuration procedure for that server type.
NT: C:\AVF\visible
Tru64 UNIX : /usr/<install-dir>/visible
You have completed your Netscape web server configuration. Continue to the Getting Started section for further instructions.
[Beginning of this topic] [Table of Contents]
If Yes is already checked, skip the remaining steps in this section and go to Task 3.
D:\AVF\visible
Tru64 UNIX : /usr/<forum-install-dir>/visible
If you are not sure that the server has been restarted, click on Server Preferences in the top frame and the On/Off link in the left frame to go to the Server On/Off form, which enables you to stop and restart the server.
[Beginning of this topic] [Table of Contents]
/<apache-install-dir>/conf/access.conf.
Insure that the
ExecCGI
option is enabled as
in the following Options statement:
# This may also be "None", "All", or any combination of "Indexes", # "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews". # Note that "MultiViews" must be named *explicitly* -- "OptionsAll" # doesn't provide it.
Options Indexes FollowSymLinks ExecCGI
You can also create a symbolic link in your DocumentRoot directory to enable the alias.
srm.conf,
establish an alias for the
Forum
/visible
directory. This alias is
included in the URL, enabling users to access Forum. Use
a simple.descriptive term, for example,
forums.
Add the following lines:
# Aliases: Add here as many aliases as you need (with no limit). The format is: # Alias fakename realname # Alias /icons/ /usr/local/etc/httpd/icons/
Alias /forums/ /<forum-install-dir>/visible/
Replace
<forum-install-dir>
with
the correct path for your Forum installation.
# AddType allows you to tweak mime.types without actually editing it, or to # make certain files to be certain types. # Format: AddType type/subtype ext1
# AddHandler allows you to map certain file extensions to "handlers", # actions unrelated to filetype. These can be either built into the server # or added with the Action command (see below). # Format: AddHandler action-name ext1
# To use CGI scripts:
AddHandler cgi-script .cgi AddType application/x-http-cgi .cgi
You have completed your Apache web server configuration. Continue to the Getting Started section for further instructions.
[Beginning of this topic] [Table of Contents]
SiteScape Forum supports the following Microsoft servers:
D:\AVF\visible
You have completed your Microsoft IIS Server configuration. Continue to the Getting Started section for further instructions.
If the only or primary purpose of this web server is to provide access to SiteScape Forum users, then you can establish a default "document," requiring your users to type less in order to reach the summit page. So, for example, instead of typing the following:
http://www.company.com/forums/aca-1/dispatch.cgi
Your users can type only the following:
http://www.company.com/forums/
To enable this feature, do the following:
aca-1/dispatch.cgi
You have completed your Microsoft IIS Server configuration. Continue to the Getting Started section for further instructions.
[Beginning of this Topic] [Table of Contents]
(By default, because SiteScape Forum uses an authentication method based on cookies, each SiteScape Forum user must have their browser configured to accept cookies, or to ask for confirmation before accepting cookies.)
A typical URL that you use to access the default summit page is as follows:
After opening your summit's URL, your browser displays the default summit, which is empty. Once you create forums (discussion and document-sharing forums, calendars, newsstands, cascaded summits, teams, and more), the summit displays only the forums to which a user has access.
To get started with Forum administration, log in as a summit administrator (wf_admin, by default). Then, click on any Help button in Forum, click on the "Admin help" toolbar button, and click on the links in the "Getting started..." section.
The first time you access the Help system (or after you upgrade your Forum installation or re-index the Help files), Forum rebuilds the system, which can take a few minutes. When Forum is finished building the system, click on either the Click here to view the Help system link or the OK button to view Help information.
[Beginning of this topic] [Table of Contents]
For more information on Forum support--or on other SiteScape products and services--please visit the SiteScape web site. Or, you can e-mail us at the following address:
support@sitescape.com
The information in this document is subject to change without notice and should not be construed as a commitment by SiteScape, Inc. SiteScape, Inc assumes no responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
SiteScape and SiteScape Forum are trademarks of SiteScape, Inc.
AltaVista is a trademark of Digital Equipment Corporation.
Tru64 UNIX is a trademark of Compaq Computer Corporation.
Java and all Java-based names and logos are trademarks of Sun Microsystems, Inc. and refer to Sun's Java Technologies. Solaris is a registered trademark of Sun Microsystems, Inc. SPARC is a registered trademark of SPARC International, Inc. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
Netscape Communications, Netscape, Netscape Navigator, Netscape Communicator, Netscape Enterprise Server, and Netscape FastTrack Server are trademarks of Netscape Communications Corporation.
Microsoft, PowerPoint, Windows NT, and Windows 95 are registered trademarks of Microsoft Corporation. Internet Explorer is a trademark of Microsoft Corporation.
Red Hat is a registered trademark of Red Hat, Inc.
Linux is a registered trademark of Linus Torvalds.
UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. UNIX and XWindow System are registered trademarks of X/Open Company, Ltd. All other trademarks and service marks are the property of their respective companies.
© SiteScape, Inc., 2000, 1999. All Rights Reserved. Produced in the U.S.A.
(Special Focus - Java Technologies)(Disc 1).ISO/products/Software/SiteScapeInc/dlogo.gif)